Efficient headunit communication integration

ABSTRACT

In an example, the mobile device may be configured to determine whether to authorize a request for the vehicle head unit to utilize a resource of the mobile device. The mobile device may be configured to utilize a proxy of the mobile device to establish a connection with a destination in response to determining to authorize the request.

PRIORITY

This application claims benefit of U.S. Provisional Application No.61/740,376 filed on Dec. 20, 2012, entitled: EFFICIENT HEADUNITCOMMUNICATION INTEGRATION, and claims priority as a continuation-in-partof U.S. patent application Ser. No. 13/605,846 filed on Sep. 6, 2012,entitled: MOBILE INTEGRATION PLATFORM (MIP) INTEGRATED HANDSETAPPLICATION PROXY (HAP), which is a non-provisional of U.S. ProvisionalApplication No. 61/533,694 filed on Sep. 12, 2011, entitled: MOBILEINTEGRATION PLATFORM (MIP) INTEGRATED HANDSET APPLICATION PROXY (HAP)and U.S. Provisional Application No. 61/538,063 filed on Sep. 22, 2011,entitled: EXTENSIBLE SCHEME FOR OPERATING VEHICLE HEAD UNIT AS EXTENDEDINTERFACE FOR MOBILE DEVICE and which is a continuation-in-part U.S.patent application Ser. No. 12/777,989 filed on May 11, 2010, entitled:CENTRALIZED MANAGEMENT OF MOTOR VEHICLE SOFTWARE APPLICATIONS ANDSERVICES, which is a continuation-in-part of U.S. patent applicationSer. No. 12/729,207 filed on Mar. 22, 2010, entitled: CENTRALIZEDMANAGEMENT OF MOTOR VEHICLE SOFTWARE APPLICATIONS AND SERVICES, which isa non-provisional of U.S. Provisional Application No. 61/252,066 filedon Oct. 15, 2009, entitled: CENTRALIZED MANAGEMENT OF MOTOR VEHICLESOFTWARE APPLICATIONS AND SERVICES and U.S. Provisional Application No.61/260,781 filed on Nov. 12, 2009, entitled: CENTRALIZED MANAGEMENT OFMOTOR VEHICLE SOFTWARE APPLICATIONS AND SERVICES, each of which isherein incorporated by reference in its entirety.

COPYRIGHT NOTICE

© 2011-2013 Airbiquity, Inc. A portion of the disclosure of this patentdocument contains material which is subject to copyright protection. Thecopyright owner has no objection to the facsimile reproduction by anyoneof the patent document or the patent disclosure, as it appears in thePatent and Trademark Office patent file or records, but otherwisereserves all copyright rights whatsoever. 37 CFR §1.71(d).

BACKGROUND OF THE INVENTION

A motor vehicle can be equipped with a “head unit” having a userinterface. The user interface can include various resource componentssuch as a screen, speakers, a microphone, a touch screen and/or keypad,etc.

Smart phones or other mobile phones (also called handsets) can downloadvarious application programs (“applications”) that operate on the phone.A user can utilize a user interface of the phone to control theapplication and/or utilize the application in some way (such as watchingthe visual display or listening to the audio output). Extendingapplications from the mobile phone to the head unit has become a popularfeature offered by various service providers and vehicle manufacturers.As a result, the user can take advantage of better user interfacecomponents offered by the head unit (e.g. a larger screen and higherquality audio output). It is desirable to provide a mechanism tocontrol, manage, and enable the extension of mobile phone applicationsto a vehicle head unit.

SUMMARY OF THE INVENTION

The following is a summary of the invention in order to provide a basicunderstanding of some aspects of the invention. This summary is notintended to identify key/critical elements of the invention or todelineate the scope of the invention. Its sole purpose is to presentsome concepts of the invention in a simplified form as a prelude to themore detailed description that is presented later.

In one example, a network device stores a mapping of applicationoperation modes to vehicle conditions such as a first condition of thevehicle powered but not moving and a second condition of the vehiclemoving. The network device receives a wirelessly transmitted request(sent by either a wireless transmitter of the vehicle or of a mobiledevice coupled to the vehicle) for a particular application to utilizean interface powered by the vehicle. The network device compares anapplication identifier specified by the received request to the mapping.The network device then identifies a portion of the vehicle interfaceaccording to the comparison and signals control software on the vehicleto grant the particular application access to only the identifiedportion of the vehicle interface. The application can reside on themobile device and utilize the vehicle interface as an extendedinterface, or the application can reside on the vehicle itself.

In an example, a processing device sends, to a remote network device, arequest for an application of a mobile device to utilize a resource of avehicle head unit, the request including a first profile of the vehiclehead unit and a second profile of the mobile device. Responsive tosending the request, the processing device receives an instruction fromthe remote network device, the instruction to be executed by embeddedsoftware of the vehicle head unit so as to enable the application toutilize a resource of the vehicle head unit.

In an example, the embedded software comprises a template Human MachineInterface (HMI) application including a plurality of HMI screens. In anexample, the template HMI application operates without an interpretercomponent.

In an example, the mobile device may be configured to determine whetherto authorize a request for the vehicle head unit to utilize a resourceof the mobile device. The mobile device may be configured to utilize aproxy of the mobile device to establish a connection with a destinationin response to determining to authorize the request.

Additional aspects and advantages of this invention will be apparentfrom the following detailed description of preferred embodiments, whichproceeds with reference to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system to control the use of a head unit as anextended interface for a phone application in a safe and intelligentmanner.

FIG. 2A illustrates a flow chart showing operation of the software 32 ofFIG. 1.

FIG. 2B illustrates a flow chart showing a contention scheme that can beused by the software 32 of FIG. 1.

FIG. 3 illustrates a flow chart showing operation of the software 30A-Bof FIG. 1.

FIG. 4 illustrates a system to select and distribute applications to avehicle in a safe and intelligent manner.

FIG. 5 illustrates a flow chart showing operation of the software ofFIG. 4.

FIG. 6 illustrates more detail of the system shown in FIGS. 4-5.

FIG. 7 illustrates a system to select and distribute applications to avehicle in a safe and intelligent manner according to user preferences.

FIG. 8 illustrates a flow chart showing operation of the software ofFIG. 7.

FIG. 9 illustrates more detail of the system shown in FIGS. 7-8.

FIG. 10 illustrates a system to select a head unit graphical interfaceaccording to a configuration of the head unit.

FIG. 11 illustrates a system to generate and send remote computingapprovals to the head unit.

FIG. 12 illustrates a system to push graphical user interface updates tothe head unit in response to the mobile device generating a request fora new application or the user web portal selecting a new application.

FIG. 13A illustrates a flow chart showing pre-operation of a parentalcontrol scheme.

FIG. 13B illustrates a flow chart showing operation of the parentalcontrol scheme.

FIG. 14 illustrates a system to operate a vehicle head unit as anextended interface for a mobile device.

FIG. 15 illustrates a signaling diagram showing one example ofoperations that can be performed by the server, the vehicle head unit,and the mobile device of FIG. 14.

FIG. 16 illustrates a system for extending a mobile phone userapplication to utilize an HMI of a vehicle head unit in accordance withone embodiment of the present disclosure.

FIG. 17 is a functional block diagram illustrating an example ofsoftware components contained in a handset application proxy (HAP)application.

FIG. 18 is a simplified diagram illustrating data flow between a userapplication program and a vehicle head unit HMI by way of an integratedHAP application.

FIG. 19 illustrates a messaging or signaling diagram showing an exampleof messaging among software components to process an event received froma head unit HMI in connection with execution of a user app on a mobilephone.

FIG. 20 illustrates a messaging or signaling diagram showing an exampleof messaging among software components to process a message receivedfrom a user app executing on a mobile phone, and if necessary generatingan update message to an HMI on a head unit.

FIG. 21 illustrates one example of a vehicle head unit with an HMI thatincludes a generic display screen.

FIG. 22 illustrates a system for efficient headunit communicationintegration.

FIG. 23 is a simplified communication diagram illustrating a smartphoneapplication enabling data exchange between an automotive infotainmentsystem (IVI) and a backend (remote server) utilizing (SOCKet Secure)SOCKS Proxy protocol.

FIG. 24 is a simplified communication diagram illustrating a smartphoneapplication providing transparent proxy server functionality to enabledata exchange between an IVI and a backend (remote server).

FIG. 25 is a simplified communication diagram illustrating a smartphoneapplication enabling data exchange between an automotive IVI and abackend (remote server) utilizing SOCKS Proxy protocol chaining.

FIG. 26 is a simplified communication diagram illustrating a smartphoneapplication providing transparent proxy server functionality to enabledata exchange between an IVI and a backend (remote server) utilizingtransparent proxy chaining.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

In one example, a user couples a phone to a motor vehicle head unitusing a wired or wireless connection for the purpose of using the headunit as an extended interface for the phone. The user may be permittedto control an application on the phone using the interface of the headunit, depending on a determination via a remote server as described inthe next paragraph. Similarly, the user may be permitted to watch orlisten to an output of the application over the interface of the headunit, depending on a determination via a remote server as described inthe next paragraph.

Novel client control software on the phone and the head unit interfaceswith novel server control software on a remote server over a wirelessconnection extending from the phone. The client control softwareidentifies a phone application to utilize the head unit as an extendedinterface.

The server control software compares the identified phone application toone or more databases accessible by the remote server. Based on thecomparison, the server control software determines whether theidentified application will be permitted to utilize the head unit as anextended interface, and if so, which components of the head unitinterface will be permitted to be used by the application. The servercontrol software signals the client control software to control thephone and head unit according to the determination. Accordingly, anyutilization of the head unit as an extended interface can be controlledin a safe and intelligent manner.

FIG. 1 illustrates a system to control the use of a head unit as anextended interface for a phone application in a safe and intelligentmanner.

The system 100 includes software 30A and 30B configured on,respectively, a mobile phone 20 (or other mobile device) and head unit21 (or other interface powered by a motor vehicle such as a userinterface integrated with a steering wheel or a user interfaceintegrated with a seat back). The software 30A and 30B interfaces withthe software 32 configured on a remote server 22 to regulate and controlwhen and how applications 40 operating on the phone 20 access I/Oresources 1-4 of the head unit 21.

FIG. 2A illustrates a flow chart showing operation of the software 32 ofFIG. 1.

In block 201, the software 32 receives a request for a particularapplication 40 on the phone 20 to utilize the interface (including input24 resources 1-2 and output 25 resources 3-4) of the head unit 21. Therequest includes a user identifier corresponding to the user of themotor vehicle and/or head unit 21, an application identifiercorresponding to the particular application 40, and vehicle statusinformation. The user identifier could be an identifier provided by theuser when the control software 30A was first activated in the mobilephone 100, user's phone number, etc.

In block 202, the software 32 authenticates the user. This can includedetermining whether the user identified by the user identifier matches adatabase 11 of subscribers for the service of extending the interface ofthe phone 20 using the head unit 21. If the user is not authenticated indiamond 203, then in block 204A the software 32 signals the software30A/B to block access by the application 40 to the head unit 21. Itshould be understood that the system 100 can be configured so that block202 is optional.

Otherwise, if the user is authenticated, then in block 204B the software32 authenticates the application 40 by comparing the applicationidentifier to a list 12 of applications (also referred to as awhitelist). This list 12 can be compared by version number such that oneparticular version of an application 40 can be identified on the listwhile a different version is excluded. If the particular application 40(or particular version) is not on the list 12 in diamond 205, then inblock 204A the software 32 signals the software 30A-B to block access bythe application 40 to the head unit 21.

Otherwise, if the application 40 is authenticated, then in block 206 thesoftware 32 compares the application identifier and the current vehiclestatus information to a mapping 15 of application operation modes. Asshown, the mapping 15 can have an entry 17 for each application 40 ofthe list 12. Each entry 17 includes a mapping that is particularized forthe corresponding application 40. For example, an entry 17 forapplication A maps the vehicle status “vehicle moving≦than X” toresources 1, 2, and 4 (namely application A will be permitted to accessthe only the screen 1, the speaker 2, and microphone 4 under thisvehicle condition) whereas the entry 17 for application C maps thevehicle status “vehicle moving≦than X” to only resources 2 and 4 (namelyapplication C will be permitted to access the speaker 2 and microphone4). One real world example might be a navigation application A and avideo game application C, where even when a passenger is present thesystem 100 will not allow the video game application C to be displayedon the head unit 21 screen 1 as this is deemed to be too much of adistraction for a driver whereas the navigation application A can bedisplayed on the head unit 21 screen 1. Another real world applicationcan be a vehicle with a plurality of interfaces, such as a head unit anda display attached to the back of a seat. An application can be grantedaccess to the back seat display under conditions where the sameapplication would not be granted access to the head unit.

It should be understood that, in other examples, the mapping 15 can bestored on the mobile phone 20. In this case, the comparison described inthe previous paragraph can be performed by the control software 30A. Insuch a case, the control software 30A checks the current vehicle statusby communicating with the head unit 21.

In block 207, the software 32 identifies a set of some or all of the I/Oresources of the head unit 21 according to the comparison. In block 208,the software 32 signals the remote software to provide the particularapplication 40 access to only those ones of the I/O resources 1-4 of theidentified set. In one example, such signaling can include controllingthe software 30A on the mobile phone 20 so that all access requests sentfrom the mobile phone 20 conform to the identified set of the I/Oresources. In another example, such signaling can include controllingthe software 30B on the head unit 21 to block access requests sent fromthe mobile phone 20 in any manner such as by simply disabling I/Oresources on the head unit 21. In yet other examples, such signaling caninclude controlling both the software 30A and the software 30B.

FIG. 2B illustrates a flow chart showing a contention scheme that can beused by the software 30B of FIG. 1. A contention scheme can be utilizedin addition to the scheme shown in FIG. 2A.

In block 209, the software 30B determines whether any of the I/Oresources of the identified set are currently in use. If none are in usein diamond 210, then in block 211A the software 30B provides theparticular application access to only those I/O resources of theidentified set.

Otherwise, if at least one of the resources of the set is in use, thenin block 211B the software 30B identifies a by-resource ranking 13 ofthe applications for each of the in-use resources of the identified set.This is shown in FIG. 1 where there is a ranking 13 for each resource1-4. In block 212, the software 30B compares the application identifierto the by-resource ranking(s) 13 to determine whether the application 40has priority for any of the in-use resources of the identified subset(the may be performed via signaling since the ranking 13 is shown on theremote server or the ranking may have been sent to the vehicle interfacein an earlier process). This comparison will indicate whether theapplication currently using a particular in-use resource is deemedhigher or lower priority than the requesting application for that in-useresource. In block 213, the software 30B provides the particularapplication 40 access to only those ones of the I/O resources 1-4 of theidentified set that are also not currently in use or are in use by alower priority application.

FIG. 3 illustrates a flow chart showing operation of the software 30A-Bof FIG. 1.

In block 301, the software 30A-B sends a request for a particularapplication 40 on the phone 20 to utilize the interface of the head unit21. In block 302, the software 30A-B receives back a signal indicatingwhether or not the application 40 is authorized to access the head unit21 at this time, and if so, an identification of which resources 1-4 canbe utilized. If the application 40 is not authorized in diamond 303,then in block 304A the software 30A-B outputs a notification that theapplication 40 is not authorized to access the head unit. Thisnotification could be output by the mobile phone 20 or the head unit 21,or both.

Otherwise, if the application 40 is authorized in diamond 303, then inblock 304B the software 30A-B controls the mobile phone 20 and the headunit 21 to cause the application 40 to be extended to the identifiedresources. If only a subset of possible resources for the application 40(from the respective mapping 17) are utilized due to a conflict, thenthe software 30A-B may generate a notification to alert the driver aboutthe lower priority application being suspended before activating thehigher priority application. In another example, if the resources arecurrently used by a lower priority application, software 30A-B canautomatically suspend/end the lower priority application and allow thehigher priority application to be activated using the requiredresources.

If it is determined that application 40 can be extended to the head-unit21, the server 22 can download corresponding “control panel” software tothe head unit to control the application 40. By having downloading thissoftware to the head unit 21 based on the application being requested, aservice provider can customize and update the “control panel”accordingly when new applications or update to existing applications areavailable. The head-unit can have a web-code renderer to display the“control panel” software.

Referring again to FIG. 1, the software 30A-B interfaces with thesoftware 32 over a wireless connection extending from the phone 20. Thiswireless connection can utilize a packet data connection (including butnot limited to GPRS, EDGE, EVDO, UTMS, WiMAX, WiFi, etc.), Short MessageService (SMS), or In-Band-Signaling modems on the mobile phone 20 andthe remote server 22 as described in U.S. Pat. Nos. 6,144,336;6,690,681; and 6,493,338.

Still referring to FIG. 1, it is noted that the mobile phone 20 cancouple to the head unit 21 by using a connection such as a USB,Bluetooth, or WiFi connection. These are just examples, however, and inother cases a different connection and/or protocol may be suitable forutilizing the interface of the head unit 21 for the application 40 ofthe phone 20.

It should be understood that the mapping 15 can have any vehiclestatuses and that the four illustrated examples are merely someexamples. For example, another vehicle status could be whether thevehicle is moving more than speed ‘X’ AND a passenger is present.

It should be understood the head unit 21 can include less than all theexample resources shown, or other resources that are not shown. Forexample, another possible I/O resource component is a text to speechcomponent.

In the illustrated example, a first application can be permitted toaccess a first subset of whichever resources are actually present on thehead unit 21 based on an intelligent decision by the system 100, while asecond different application can be permitted to access a second subsetof the resources, or even all of the resources.

It should be understood that the applications 40 can be ranked “byresource” as illustrated or there can be a single ranking including allthe applications 40. The system 100 is implemented with the “byresource” ranking as shown, but the concepts described herein could beimplemented in another system that ranks applications independently ofresource.

FIG. 4 illustrates a system to select and distribute applications to avehicle in a safe and intelligent manner.

One difference between the previously discussed system of FIG. 1 and thesystem of FIG. 4 is the install location for applications. Whereas theapplications A-C in the system 100 of FIG. 1 are installed and operatingon the mobile phone 20 (using the head unit 21 or other interfacepowered by the vehicle as an extended interface), the applications J-Lin the system 200 of FIG. 4 are installed on the head unit 221 or othercomponent powered by the vehicle. In system 200 of FIG. 4, the software230-232 enables a provider to select which applications can be installedon the head unit 221 and control distribution of the selectedapplications to the vehicle.

Before discussing the details of system 200 in the following paragraphs,it should be apparent that the structures and functions of system 100described in FIGS. 1-3 can be combined with the structures and functionsof system 200 (FIGS. 4-6) into a single system. For example, a singlesystem could include some applications installed on a mobile phone usingan interface of a vehicle as an extended interface and some applicationsinstalled on a component of the vehicle.

FIG. 5 illustrates a flow chart showing operation of the software ofFIG. 4.

In block 501, in response to the vehicle being powered up, the controlsoftware 230 sends a signal 244 to the server 222 indicating vehiclepower-up. The signal 244 can be sent over a local connection such as aUSB or Bluetooth connection to be relayed by the mobile device 220 overa wireless telecommunications network.

In block 502, the software 232 checks a download directory 239(sometimes referred to as a “sandbox”) associated with the vehicle todetermine if there are any applications to be downloaded to the vehicle.A scheme for intelligently selecting applications that are present inthe download directory 239 will be discussed in detail later withreference to FIG. 6.

If the check by the software 232 indicates that the download directory239 includes at least one application, the process continues. For now,let it be assumed for the purposes of illustration that the downloaddirectory 239 includes applications 240 (J-L). Accordingly, in block 503the software 232 generates and sends signaling 245 to cause the IPgateway software 231 on the mobile phone 220 to operate as an IP gatewayfor forwarding applications to the head unit 221. In one example,signaling 245 includes communications to dynamically load the mobilephone 220 with the software 231 in response to the determination inblock 502 and cause the software 231 to operate thereon for the downloadto vehicle. The signaling 245 may not take place if the mobile phone 220is already loaded with the software 231 and ready for IP gatewayoperation. In other examples, the signaling 245 could originate from thecontrol software 230 on the head unit 221 in response to detectingvehicle power-up.

In block 504, the software 232 generates and sends IP packets 250 todownload the applications 240 onto the vehicle. The IP packets 250 arereceived by the mobile phone 220 and forwarded by operation of thesoftware 231 to the head unit 221. In block 505, the software 230receives the IP packets 230 and installs the applications 240 (J-L) onthe vehicle (installation can be on components of the head unit 221 orother vehicle components).

Thereafter, a user of the vehicle can operate the applications J-L usingthe head unit 221 as an interface. It should be understood that thesoftware 230 and 232 can operate according to any of the principlesdescribed in FIGS. 1-3. For example, the software 230 and 232 canregulate utilization of the I/O resources of the head unit 221 by theactive application(s) according to current vehicle status. As anotherexample, in systems where applications are installed on both the vehicleand a mobile device, the software 230 and 232 can include allapplications that utilize the vehicle interface in an applicationranking/priority table similar to the table 13 (FIG. 1).

In one example, the head unit 221 includes a web code renderer 299, forexample an HTML renderer, controlled via the software 230. The web coderenderer 299 is configured to display HTML code, but unlike a browser,does not allow a user to freely navigate to web locations. Specifically,the web code renderer 299 displays only applications allowed by theprovider, e.g. specified by the server 222.

It should be understood that the flow chart described above addressesupdating applications installed on the vehicle. The vehicle can also bepre-loaded with certain applications so that some of the applicationsinstalled on the vehicle are downloaded according to the flowchart whileothers are installed thereon during manufacturing.

Thus, based on the principles described above, vehicles can bemanufactured with none of the applications installed on the vehicle butinstead the applications can downloaded to the vehicles when the driversare present in the vehicles. The types of applications downloaded to thevehicles are governed by preferences defined in the network serverprovided by the drivers.

FIG. 6 illustrates more detail of the system shown in FIGS. 4-5.

It was previously explained that the server 222 includes a downloaddirectory 239 of applications waiting to be downloaded on a per-vehiclebasis. FIG. 6 illustrates the user web portals 601, 604, and 605 thatcan be involved in selection of the applications in the downloaddirectory 239 and describes an example use of these web portals 601,604, and 605.

A provider such as an OEM of the vehicle operates the web portal 601.Using an interface such as a computing terminal 625, the providercontrols an application selection portion 608 of the web portal 601 withcommunications 650 to assemble the controlled list 610 of applicationsfrom the list 609 of all applications that can be installed on thevehicle. Typically building the list 610 from the list 609 involvesvalidation of the applications from a technical standpoint and/or abusiness standpoint of the provider.

The provider also sends communications 651 to select applications fromthe controlled list 610 to be installed on a particular vehicle. Theseselections may be based on a mapping a vehicle models to applications,for example. These selections 652 fed into the download directory 239.

Regarding the list of all available applications 609, it should beunderstood that this list can be assembled by applications developed bythe provider and/or third parties. In the case of third partiesproviding applications, the third party uses the application submission618 portion of the web portal 604 (which is hosted by a web serveroperated by the provider in one example) to submit an application 649 tobe included in the list 609.

A vehicle user can also select applications to be included in thedownload directory 239 using a computing terminal 626, for example usingany internet accessible computing device such as the mobile device or adesktop computer. The computing terminal 626 accesses the applicationselection portion 628 of the user web portal 605 (which is hosted by aweb server operated by the provider in one example) to view thecontrolled list 610 of applications that can be installed on hisvehicle. The user can then send communications 661 to selectapplications from the controlled list 610 that the user would likeinstalled on his vehicle. These selections 662 are fed into the downloaddirectory 239.

The user web portal 605 can also be configured to allow a user to removeparticular applications from the download directory 239, e.g. the usermay desire to remove one of the provider selected applications 652 addedto the download directory 239 via the provider. Removal can be bydeletion of an application already sent to the directory 239 or byindicating that a particular application is not desired before suchapplication is ever added to the download directory 239.

According to the above, applications can be accumulated into theper-vehicle download directory 239. At vehicle power-up, suchapplications can be downloaded and installed onto the vehicle. Thedownload directory 239 can then accumulate new applications until a nextvehicle power up.

It should be understood that an interface similar to that of the webportal 605 can be displayed on the head unit of the vehicle. The usercould then make selections from such interface for selectingapplications from the controlled list 610. The selected applicationscould be downloaded immediately to the vehicle instead of being put inthe download directory when the selections are made from the interface.

FIG. 7 illustrates a system to select and distribute applications to avehicle in a safe and intelligent manner according to user preferences.

One difference between the previously discussed system of FIG. 1 and thesystem of FIG. 7 is the install location for applications. Whereas theapplications A-C in the system 100 of FIG. 1 are installed and operatingon the mobile phone 20 (using the head unit 21 or other interfacepowered by the vehicle as an extended interface), the applicationsM-P/Q-S in the system 300 of FIG. 7 are installed on the head unit 321or other component powered by the vehicle. In system 300 of FIG. 7, thesoftware 330-332 enables a provider to select which applications can beinstalled on the head unit 321 and control distribution of the selectedapplications to the vehicle.

Before discussing the details of system 300 in detail in the followingparagraphs, it should be apparent that the structures and functions ofsystems 100 and 200 described in FIGS. 1-6 can be combined with thestructures and functions of system 300 (FIGS. 7-8) into a single system.For example, a single system could include some applications installedon a mobile phone using an interface of a vehicle as an extendedinterface and some applications installed on a component of the vehicle.

FIG. 8 illustrates a flow chart showing operation of the software ofFIG. 7.

In block 801, the head unit 321 communicatively couples to a mobiledevice such as mobile phone 320. In one example, the connection 540 isestablished via Bluetooth pairing of the head unit 321 and the mobilephone 320. The Bluetooth pairing can be in response to the vehicle beingpowered up (causing the head unit to power up and search for a Bluetoothdevice), although it should be apparent that Bluetooth pairing couldresult from other circumstances such as the mobile phone 320 poweringup, the mobile phone 320 being brought within range of the head unit321, re-pairing after another Bluetooth device is disconnected from thehead unit 321, etc. In other examples, the communicative connection canbe established by a user connecting the mobile phone 320 to the headunit 321 using a USB connection.

In block 802, the control software 330 accesses a telephone number ofthe mobile phone 320. It should be understood that mobile phones areactivated with a particular phone number in conjunction with subscribingto a call plan, which is the phone number the control software 330 readsfrom the mobile phone 320. In one example, the signaling 542 to obtainthe phone number is performed using Bluetooth signaling.

In block 803, the control software 330 sends signaling 543 to the server322. The signaling 543 can be sent over a local connection such as aUSB, Bluetooth, or WiFi connection to be relayed by the mobile device320 over a wireless telecommunications network. The content of thesignaling 543 can be similar to the signal 244 described in more detailpreviously with respect to FIG. 4, but in addition, can provide theobtained phone number.

In block 804, the control software 332 compares the phone numberincluded in the signaling 543 to the mapping 350. The mapping correlateseach of a plurality of download directories A-B accessible via thisparticular head unit 321 to a particular phone number. For example, inthe mapping a first phone number is correlated with the downloaddirectory A and a second phone number is correlated with the downloaddirectory B. The control software 332 selects one of the downloaddirectories A-B based on the comparison of the received telephone numberto the mapping 350.

The software 332 then checks the selected one of the downloaddirectories A-B to determine if there are any applications currentlystored in the selected directory. A scheme for intelligently selectingapplications that are present in the download directories A-B will bediscussed in detail later with reference to FIG. 9. For now, let it beassumed for the purposes of illustration that the download directories339A and 339B currently include applications 340A (M-P) and 340B (Q-S),respectively, in addition to the head unit frontend configurations 369Aand 369B.

As noted briefly in the previous paragraph, the download directories A-Binclude head unit frontend configurations A-B, respectively, in additionto the applications 340A and 340B. The configurations A-B can be storedas HTML code or other web code compatible with the web code renderer ofthe 399. Depending on which one of the head unit frontend configurationsA-B is downloaded to the head unit 321, a display 380 of the head unit321 will display a different graphical user interface. Each of thedifferent web code files 369A and 369B will produce a differentgraphical user interface when displayed using the display 380 and therenderer 399. For example, each graphical user interface could have itsown user customized settings such as a particular wallpaper selected bya user. A scheme for generating the different head unit frontendconfigurations A-B will be discussed in detail later with reference toFIG. 9.

In block 805, the software 332 generates and sends signaling to causethe IP gateway software 331 on the mobile phone 320 to operate as an IPgateway for forwarding applications to the head unit 321 similar to thescheme described in FIG. 4. In one example, similar to FIG. 4, suchsignaling includes communications to dynamically load the mobile phone320 with the software 331 to cause the software 331 to operate thereonfor the download to vehicle. This signaling may not take place if themobile phone 320 is already loaded with the software 331 and ready forIP gateway operation. In other examples, the signaling 345 couldoriginate from the control software 330 on the head unit 321 after theconnection 540 is established.

In block 806, the software 332 generates and sends IP packets 545 todownload the data from the selected one of the directories onto thevehicle, e.g. either applications M-P and configuration A orapplications Q-S and configuration B. The IP packets 545 are received bythe mobile phone 320 and forwarded by operation of the software 331 tothe head unit 321. It should be understood that in this particularillustration the IP packets 545 include both applications and aconfiguration for the graphical user interface, but in other scenariosthe IP packets 545 might contain either an application or aconfiguration. Also, it should be apparent that, if there are noapplications currently in the selected download directory and there havebeen no changes to the configurations stored in the download directorysince a previous download, then the IP packets 545 may not be sent.

In block 807, the software 330 receives the IP packets 545 and installsthe applications included therein on the vehicle (installation can be oncomponents of the head unit 321 or other vehicle components). Thesoftware 330 also processes the configuration from the IP packets 545using the web code renderer 399 to generate a particular graphical userinterface based on the detected phone number.

Thereafter, the graphical user interface output via the display 380 willcorrespond to one of the configurations A-B stored in the selecteddownload directory. A user of the vehicle can operate the installedapplications M-P or Q-S using the head unit 321 as an interface.

It should be understood that the software 330 and 332 can operateaccording to any of the principles described in FIGS. 1-3. For example,the software 330 and 332 can regulate utilization of the I/O resourcesof the head unit 321 by the active application(s) according to currentvehicle status. As another example, in systems where applications areinstalled on both the vehicle and a mobile device, the software 330 and332 can include all applications that utilize the vehicle interface inan application ranking/priority table similar to the table 13 (FIG. 1).

In the example described above, the control software 330 accesses aphone number of the mobile phone 320 to uniquely identify the mobilephone 320 from other mobile phones. In other examples, control softwareon the head unit 321 can access a different value on a communicativelycoupled mobile phone to uniquely identify the mobile phone from othermobile phones. Other examples of values can include, but are not limitedto, a physical address of the mobile phone. In such other examples, itshould be apparent that such values are used in the mapping, e.g. if theother values are physical addresses then the mapping includes physicaladdresses correlated to download directories.

In the example described above, the control software 330 sends theaccessed unique identifier (phone number in this example) to the server322. In other examples, the mapping 350 can be stored on the vehicle. Insuch a case, the control software 330 identifies a particular downloaddirectory listed in the mapping according to the comparison and sends anidentifier specifying the particular download to the server 322. Theserver 322 may then respond with IP packets 545 sending data from theidentified download directory.

FIG. 9 illustrates more detail of the system shown in FIGS. 7-8.

It was previously explained that the server 322 includes a plurality ofdownload directories 339A-B of applications waiting to be downloaded.FIG. 9 illustrates the user web portal 905 that can be involved increating the download directories 339A-B and selection of theapplications on a per-directory basis and describes an example use ofthis web portal 905.

A vehicle user can create a plurality of profiles corresponding to thevehicle using the profile creation portion 930 of the user web portal905. A profile can be created for each person that may use the vehicle.A field 927 requests a unique phone number or other unique identifier ofa mobile phone respectively corresponding to each person. A name of eachperson or other information for each person may be gathered with thephone number(s). After or during profile creation, server 322 creates adownload directory for each profile and updates the mapping 350 for eachnumber/directory combination. In some examples, the portion 930 can beconfigured to allow a user to rank the created profiles so that, if thehead unit can be coupled to more than one of the mobile devicessimultaneously (it can depend on the connection protocol whether this ispossible), a higher ranked one of the corresponding profiles will beused.

During or after profile creation the web portal 905 can be operated toselect applications to be included in the download directories 339A-Busing a computing terminal 926, for example using any internetaccessible computing device such as the mobile device or a desktopcomputer. The computing terminal 926 accesses the application selectionportion 928 of the user web portal 905 (which is hosted by a web serveroperated by the provider in one example) to view the controlled list ofapplications that can be installed on the vehicle. The user can thensend communications 961 to select applications from the controlled listthat the user would like installed on his vehicle on a per-directorybasis. These selections 962 are respectively fed into the downloaddirectories 339A-B on a per-directory basis.

The user web portal 905 can also be configured to allow a user to removeparticular applications from the download directories 339A-B, e.g. theuser may desire to remove one of the provider selected applications 952added to the download directory 339A or 339B via the provider on aper-directory basis. Removal can be by deletion of an applicationalready sent to the download directory 339A or 339B, or by indicatingthat a particular application is not desired before such application isever added to the download directory 339A or 339B.

The user web portal 905 can also include a head unit frontendconfiguration customization portion 928. This portion 928 allows newconfigurations 369A-B to be added to the download directories 339A-B,with each person's configuration customized according to their requests.For example, a first wallpaper background can be added to the downloaddirectory 339A and a second different wallpaper background can be addedto the download directory 339B. Other customizations can includecustomized graphical interface buttons, customized graphical userinterface layout, custom images, etc.

According to the above, applications can be accumulated into theper-vehicle download directories 339A-B on a per-directory basis. Uponthe head unit coupling to a particular one of the mobile devices, datafrom a corresponding one of the download directories 339A-B can bedownloaded and installed onto the vehicle to provide a customizedapplication set and a customized user interface.

It should be understood that an interface similar to that of the webportal 905 can be displayed on the head unit of the vehicle. The usercould then make selections from such interface for selectingapplications from the controlled list. The selected applications couldbe downloaded immediately to the vehicle instead of being put in thedownload directory when the selections are made from the interface.

FIG. 10 illustrates a system to select a head unit graphical interfaceaccording to a configuration of the head unit.

The system 1000 includes a server 1022 and a head unit 1021 that caninclude components similar to any of the previously described serversand head units. It should be appreciated that the server 1022 and thehead unit 1021 communicate using a mobile device (not shown) that iscoupled to the head unit 1021. The head unit 1021 includes controlsoftware 1030 and the server 1022 includes control software 1032.

The software 1032 identifies a configuration of the head unit 1021, forexample, by probing 1081 the head unit 1021 to collect information. Thesoftware 1030 responds 1082 with information identifying theconfiguration of the head unit 1021. The response 1082 can include atleast one of the following: a make/model/year of the vehicle, apredefined code, or an ad hoc listing of the configuration of the headunit 1021 (such as color/monochrome display, native resolution, etc.).

The software 1032 then selects from a plurality of graphical userinterfaces based on the head unit information 1082. For example, if thehead unit information 1082 includes a predefined code, the software 1032can compare the code to a stored mapping 1085 of codes to graphical userinterfaces Y-Z. The selected graphical user interface corresponds to aparticular configuration of the head unit 1021 as reported by theinformation 1082. For example, if the head unit 1021 has a monochromedisplay, the selected Graphical User Interface (GUI) may be interface Y,whereas if the head unit 1021 has a color display, the selected GUI maybe interface Z. Or, perhaps if the head unit 1021 has a nativeresolution of a first value, the selected GUI may be interface Y,whereas if the head unit 1021 has a native resolution of a second value,the selected GUI may be interface Z. If the make/model/year of the carindicates an interior of a first design, say a luxury motif, theselected GUI may be interface Y, whereas if the make/model/year of thecar indicates an interior of a second design, say a sporty motif, theselected GUI may be interface Z.

Once a graphical user interface has been selected, the software 1032conducts an IP packet transfer 1045 of the selected one of the graphicaluser interfaces Y-Z. It should be understood that the IP packet transfer1045 may utilize the previously-described IP gateway software of themobile phone (not shown). The software 1030 automatically installs thereceived graphical user interface. The selected graphical user interfacecan replace a default graphical user inference 1090 or previouslydownloaded graphical user interface residing on the head unit 1021 priorto the transfer 1045.

It should be understood that the previously described frontendconfigurations can be applied to the selected and installed GUI. Forexample, a selected GUI can be installed on the head unit 1021, and thenfurther modified in appearance based on a customized frontend selectionaccording to a telephone number of the mobile device currently coupledto the head unit 1021.

FIG. 11 illustrates a system to generate and send remote computingapprovals to the head unit.

The system 1100 includes a server 1122 and a head unit 1121 that caninclude components similar to any of the previously described serversand head units. It should be appreciated that the server 1122 and thehead unit 1121 communicate using a mobile device 1131. The head unit1121 includes control software 1130 and the server 1122 includes controlsoftware 1132.

The head unit 1121 includes a remote desktop viewing program such as aVirtual Network Computing (VNC®) client 1148 to connect to the VNCserver 1149 running on the mobile device 1131. By way of background, aVNC client and server communicate to display the server's desktop orother current view on the client's display. The human interfacesdevice(s) directly connected to the client, e.g. keyboard, mouse, etc.,can then be used in conjunction with the displayed image to remotelycontrol the computing device running the VNC server. If an applicationis running in full screen mode on the computing device with the VNCserver, then the computing device with the VNC server controls thatapplication (rather than the entire desktop).

The control software 1130 receives a request 1155 from the mobile device1131 specifying a particular application X (1140). The control software1130 identifies the application identifier corresponding to the request1155 either by extracting the identifier itself from the request 1155 orusing a lookup based on information gleaned from the request or from anycommunication with the mobile device 1131. The control software 1130sends the communication 1156 containing the application identifier.

The control software 1132 compares the application identifier to aninternal table and generates a VNC approval 1157 for the application X.The VNC approval 1157 specifies the particular conditions under whichVNC is approved in conjunction for this application X. For example, ifthe application X is a navigation application, the approval 1157 mightspecify that VNC is approved when the vehicle is stopped or moving. Incontrast, if the application X is a media creation application, theapproval 1157 might specify that VNC is approved only when the vehicleis stopped.

The VNC approval 1157 can also specify different approvals based onwhether the application is currently running in full screen mode orwindowed mode. For example, the navigation application might be approvedwhen the vehicle is moving, but only as long as the navigationapplication is running on the mobile device 1131 in full screen mode.This will prevent VNC functionality immediately if the user switches thenavigation application into windowed mode while the vehicle is moving.

The VNC approval 1157 can also specify telephone numbers. For example,VNC can be permitted when the mobile device 1131 is running a mediaplayer application, but only if the mobile device has a particulartelephone number (this can be used as a form of parental control).

The control software 1130 stores the received VNC approval 1157 in adatabase 1135 of VNC approvals. The control software 1130 continuouslymonitors conditions based on the VNC approvals stored in the database1135 to generate the control signal 1160. The control signal 1160controls whether a view 1161 of the mobile device 1131 can be currentlydisplayed on a display of the head unit 1121 by the VNC client 1148. Thecontrol signal 1160 also controls whether inputs made using an inputinterface of the head unit 1121 will be sent 1162 to the VNC server1149.

FIG. 12 illustrates a system to push graphical user interface updates tothe head unit in response to the mobile device generating a request fora new application or the user web portal selecting a new application.

The system 1200 includes a server 1222 and a head unit 1221 that caninclude components similar to any of the previously described serversand head units. It should be appreciated that the server 1222 and thehead unit 1221 communicate using a mobile device 1231.

The server 1222 can receive an indication of a new application to beused in the system 1200 in at least two different forms (the term newapplication refers to an application that has not previously beendownloaded to the head unit 1221 and/or utilized the head unit 1221 asan extended interface). In one form, the mobile device 1231 sends anindication of a new application X (1240) to utilize the head unit 1221as an extended interface. More specifically, this indication is anapproval request 1271 generated and sent by the control software 1230 inresponse to receiving a request 1270 from the mobile device 1231.

Another way the server 1222 can receive an indication of a newapplication is from control over the user web portal 1205. The user webportal 1205 is similar to the previously described web portals. Using anapplication selection tool 1228, a user can use any remote computer toselect applications to be included in a corresponding download directory(not shown) for installation on the head unit. Thus, a receivedselection 1274 including a new application is another form of indicationof a new application to be used in the system 1200.

In response to detecting such an indication, the control software 1232determines whether to transmit an IP packet transfer 1245 including agraphical user interface update for the new application X. It should beapparent that no such IP packet transfer will be sent if the newapplication X is not included in the previously discussed controlledlist of applications (FIG. 6). In one example, the graphical userinterface update modifies a previously selected and installed graphicaluser interface (FIG. 10) to add an icon for accessing the newapplication X. In another example, the graphical user interface updateincludes any other form of update to a previously selected and installedgraphical user interface for operating new application X. The controlsoftware 1230 automatically installs the update in response to thesending of the request 1270 and/or the selections 1274. It should beapparent that the transfer 1245 can be included with a download of theapplication itself in the case that the download is waiting for vehiclepower up in a download directory.

FIG. 13A illustrates a flow chart showing pre-operation of a parentalcontrol scheme.

In block 1301, the server designates at least one profile as beingsubject to parental control. This profile can be selected by the accountholding, for example, by marking a selection using the web portal.

In block 1302, the server receives a login for a user designated as aparent (typically the account holder) for the profile subject toparental control. In block 1303, the server causes a list ofapplications associated with the profile subject to parental control tobe displayed using the web portal.

In block 1304, after displaying the list, the server receives selectionsfrom the displayed list. The server may store these selections in theprofile that is subject to parental control. The selections can includeapplications from the list and/or more detailed information in the caseof a conditional approval (a conditional approval is discussed later inmore detail).

FIG. 13B illustrates a flow chart showing operation of the parentalcontrol scheme.

In block 1320, in response to a mobile phone communicatively couplingwith the head unit, the head unit obtains a telephone number of themobile phone to be used to communicate with the server. In block 1321,the head unit sends the phone number to the server for analysis. If theobtained phone number does not match a profile designated as subject toparental control, then the parental control process completes in block1322.

Otherwise, if the obtained phone number does correspond to the profilesubject to parental control, then in block 1323 the server executesparental control. In one example, such execution includes blocks1323-1327, similar to the VNC approval process, discussed in the nextparagraph.

In block 1323, the server transmits a parental control message to thehead unit. In block 1324, the head unit continuously monitors conditionsbased on the parental control message. In block 1325, the head unitblocks a particular application from using the head unit as an extendedinterface and/or blocks a particular application installed on the headunit from running. For example, the head unit might receive anindication that the particular mobile phone has received a telephonecall, but then block the use of the head unit as an extended interfacefor the telephone call. Or, the head unit might block an attempt to runa media player application on the head unit in another example. Thecontinuous monitoring may be facilitated by a database on the head unitstoring received parental control messages.

In block 1326, the head unit conditionally blocks a particularapplication from using the head unit as an extended interface and/orrunning directly on the head unit. For example, the head unit mightreceive an indication that the particular mobile phone has received atelephone call, but then block the use of the head unit as an extendedinterface conditionally based on a value of a caller ID field on theincoming call. More specifically, the parental control message mightdesignate certain telephone numbers as exceptions to preventing the headunit from providing an extended interface for the telephone. The headunit obtains the caller ID value from the mobile phone and blocks themobile phone from utilizing an interface of the head unit conditionally.In another example, the head unit might block an applicationconditionally based on a condition of the vehicle, e.g. the head unitblocks the mobile phone from utilizing an interface of the head unitonly if the vehicle is currently moving.

In block 1327, the head unit does not block the particular applicationif the application is permitted according to the parental controlmessage. In this case, the head unit allows the application to operateaccording to approval by the server, e.g. according to whether theapplication is on the controlled list (FIG. 6).

It should be apparent that, in other examples, a system can enforce aparental control scheme using different processes than thosespecifically described above. For example, in another example, theprocesses of blocks 1323-1327 are not used. Instead, the head unitcontinuously reports conditions and application requests to the server,which dynamically withdraws a current approval according to the parentalcontrol settings. The server then controls the head unit to block acurrent disapproved application.

Extensible Scheme for Operating Vehicle Head Unit as Extended Interfacefor Mobile Device

There are known schemes for operating a vehicle head unit as an extendedinterface for a mobile device. However, in the known schemes, theconfiguration of the vehicle head unit is fixed at manufacture, and as aresult, may be inoperable with newly released mobile applications. In apartial solution, the new mobile device application is downloaded to thevehicle head, which requires the vehicle head unit to be manufacturedwith relatively expensive hardware components to enable the download,installation, and operation of the mobile device application (on thevehicle head unit).

FIG. 14 illustrates a system to operate a vehicle head unit as anextended interface for a mobile device.

The system 1400 includes a server 1411, a vehicle head unit 1412, and amobile device 1413 (which may be a long range wireless device, e.g. acell phone, in one example), including processing devices 1408, 1409,and 1410, respectively. The vehicle head unit 1412 includes a shortrange input/output interface, such as a Bluetooth transceiver or a USBport, configured to couple the vehicle head unit 1412 to an availablemobile device, such as mobile device 1413. Connection 1415 representsthe connection between the vehicle head unit 1412 and the mobile device1413. The server 1411 includes a network interface configured tocommunicate with the vehicle head unit 1412. The communications 1416from the server 1411 may arrive at the vehicle head unit 1412 over theconnection 1415 in one example (in some cases a vehicle head unit mayutilize a long range radio of the mobile device to communicate with aremote network), or through another path (in some cases a vehicle headunit may utilize a long range radio of the vehicle to communicate with aremote network).

The server 1411 contains a memory storing groups of one or moreapplication instruction(s) 1425 (each group corresponding to a mobiledevice application). The application instruction(s) of a group can beupdated over time as mobile device applications are released. Thevehicle head unit contains embedded software such as HMI application1421, which, in contrast, can be fixed at the time of manufacture of thevehicle head unit 1412. The template HMI application 1421 is a “thinclient” that is configured to execute a downloaded applicationinstruction. The template HMI application 1421 again can be referred toas a “thin client” and operates independently of an interpreter, i.e. acomponent that interprets a scripting language, e.g. Java script, intoanother programming language. The template HMI application 1421 mayinclude a plurality of generic display screens, e.g. a plurality of HMIscreens 1423.

Many applications screens on head units can be generalized as one of aplurality of screen types. In an example, the plurality of screen typesincludes information type screens, e.g. screens that show lists ofinformation, interaction type screens, e.g. screens to show aninteractive messages such as a social networking post or email message,content display screens, e.g. screens that display now playing contentsuch as content from a music application or a book application.Accordingly, in an example, the plurality of HMI screens 1423 includesan information screen, a content display screen, and an interactivemessage screen. A combination of the plurality of generic displayscreens, e.g. the plurality of HMI screens 1423, can be combined to formthe screens of a given application. The individual template format maynot change from one given application to another given application, justthe content, images if any, order in which the screens are displayed,and button mapping to application function which is residing on thephone change from one given application to another given application.

The processing device 1408 is configured to download at least one of thegroups of application instruction(s) 1425 to a memory 1450 of thevehicle head unit 1412. The download may occur at any time, but in oneexample may occur responsive to receiving a request from the processingdevice 1409 or the processing device 1410.

The download of a group of application instruction(s) may also beresponsive to determining that the application of the mobile device 1413is authorized to utilize a resource of the vehicle head unit 1412 basedon a current status of the vehicle. It should be appreciated that thedetermination of whether the application is authorized may involve anycombination of the principles described herein with reference to FIGS.1-13B. In an example, the downloading may not occur responsive todetermining that the application is not authorized to utilize theresource of the vehicle head unit 1412. In an example, the downloadingmay still occur responsive to determining that the application is notauthorized to utilize the resource of the vehicle head unit 1412, butthe server 1411 may prevent the application from utilizing the resourceof the vehicle head unit 1412 at this time.

The downloaded application instruction(s) is configured to, whenexecuted by the template HMI application 1421, instruct the template HMIapplication 1421 on how to control the particular mobile deviceapplication 1414, including what commands can be understood by theparticular mobile device application 1414 and/or a format of thosecommands. Stated more generally, the downloading and execution of theapplication instruction(s) enables the template HMI application 1421(which may be the original HMI application installed on the vehicle headunit at the time of its manufacture) to control the newly discoveredparticular mobile device application 1414 (which may be a “new” mobiledevice application, i.e. released or even developed post manufacture ofthe vehicle head unit).

In an example, the instruction delineates a specific order to display atleast a portion of the plurality of HMI screens for the requestedapplication. In other words, the specific order for the requestedapplication may be different than a specific order corresponding toanother application (each instruction for a plurality of applications ofa mobile device may delineate a different order). It should beappreciated that one application may use a different portion of theplurality of HMI screens than another application (for example, onegiven application may use all the screens, while another givenapplication may use only one of the screens).

If responses can be expected to be sent from the particular mobiledevice application 1414 to the template HMI application 1421, then thedownloaded application instruction(s) may be configured to, whenexecuted by the template HMI application 1421, provide the template HMIapplication 1421 with a format/structure of the response, includinginformation describing how the template application 1421 is to displayinformation included in the response. If responses can be expected to besent from the particular mobile device application 1414 to the templateHMI application 1421, then the downloaded application instruction(s) maybe configured to, when executed by the template HMI application 1421,provide the template HMI application 1421 with a list of commands andresponses that make up the order and sequence of messages exchangedbetween the template HMI application 1421 and the mobile deviceapplication 1414 for the involved use case.

FIG. 15 illustrates a signaling diagram showing one example ofoperations that can be performed by the server, the vehicle head unit,and the mobile device of FIG. 14.

After the vehicle head unit 1412 and the mobile device 1413 are coupled,the vehicle head unit 1412 provides a vehicle head unit profile to themobile device 1413 (signal 1502). The vehicle head unit profile mayinclude a unique identifier for the vehicle head unit 1412. The vehiclehead unit profile may include a list of all groups of applicationinstruction(s) currently stored on the vehicle head unit 1412. In anexample, the vehicle head unit profile also identifies at least onelanguage or protocol supported by the vehicle head unit 1412.

The mobile device 1413 provides a mobile device profile and the vehiclehead unit profile to the server 1411 (signal 1503). The mobile deviceprofile may include a unique identifier, e.g. a unique identifier of themobile device or a user account identifier, that is different than theunique identifier for the vehicle head unit 1412. The mobile deviceprofile may include a list of all applications currently stored on themobile device 1413 (although in some examples the unique identifier maycorrespond to the user account allowing the server 1411 to ascertain allapplications currently associated with the user account based on theaccount identifier). In an example, the mobile device 1413 identifiesTemplate HMI application(s) 1421 supported by the vehicle head unit 1412and identifies application(s) 1414 to operate with the Template HMIapplication(s) 1421.

The server 1411 downloads an application instruction 1425, e.g. a set ofapplication instructions, to the mobile device 1413 (signal 1507). In anexample, the server 1411 may download application logic, e.g. logicconfigured to command/control a particular application, corresponding toan identified application. In an example, a downloaded applicationinstruction comprises a result of a command executed by thecorresponding application logic. The download for the vehicle head unit1412 may comprise an update to an application instruction(s) from thelist, or a new application instruction(s) not yet stored on the vehiclehead unit 1412. Similarly, a download for the mobile device 1413 may bean update for an existing application of the mobile device 1413, or adownload for a new application.

The mobile device 1413 stores any received application logic in localmemory and provides the vehicle head unit 1412 with the downloadedapplication instruction(s) 1425 (signal 1508). The application logicstored in the memory of the mobile device 1413 may be executedresponsive to a user input received by the mobile device 1413.

If the vehicle head unit 1412 receives an application instruction, thevehicle head unit 1412 may build a graphical user interface withsoftware buttons for a mobile device application that can utilize thevehicle head unit 1412 as an extended interface (signal 1509). Thedisplayed GUI may utilize one of the HMI screens 1423 (FIG. 14) of thetemplate HMI application 1421 (FIG. 14). In response to a user inputselecting a mobile device application to utilize the vehicle head unit12 as an extended interface, the vehicle head unit 12 executes acorresponding one of the downloaded application instruction(s) (signal1511). The vehicle head unit operates the template HMI application basedon a result of the executing the corresponding applicationinstruction(s) (signal 1513).

In one example use case, executing a first instruction of a group ofapplication instructions causes the vehicle head unit to send aparticular message to the mobile device application to cause the mobiledevice application to respond by sending back content to the vehiclehead unit. In this example use case, the next instruction in the groupcauses the vehicle head unit to compare some or all of the content to aparameter or value contained in the next instruction. Depending on aresult of the comparison, the vehicle head unit may proceed to the nextinstruction, or proceed directly to another instruction after the nextinstruction, or display a certain text of a screen, or wait for a userto enter a selection via an interface of the vehicle head unit, orcomplete, etc., depending on the particularities of the executedinstruction.

In an example operating according to the principles described withreferences to FIGS. 14 and 15, application logic for the application toutilize a resource of the vehicle head unit is distributed between amobile device and the vehicle head unit. In another example operatingaccording to the principles described with references to FIGS. 14 and15, all of the code associated with the application logic is stored onthe mobile device.

In an example, a memory device having instructions stored thereon that,in response to execution by a processing device, cause the processingdevice to perform operations is provided. An operation includes couplinga mobile device and a vehicle head unit. An operation includes sending,to a remote network device, a request for an application of the mobiledevice to utilize a resource of the vehicle head unit, the requestincluding a first profile of the vehicle head unit and a second profileof the mobile device. An operation includes, responsive to sending therequest, receiving an instruction from the remote network device, theinstruction to be executed by embedded software of the vehicle head unitso as to enable the requested application to utilize a resource of thevehicle head unit.

In an example, the embedded software comprises a template HMIapplication and a plurality of HMI screens, and the instructiondelineates a specific order to display at least a portion of theplurality of HMI screens for the requested application. In an example,the template HMI application operates without an interpreter component.

In an example, the first profile identifies a first unique identifierthat corresponds to the vehicle head unit and identifies a language orprotocol associated with the embedded software. In an example, thesecond profile identifies a second unique identifier that is differentthan the first unique identifier.

In an example, the instruction comprises a result of a command orcontrol function executed by application logic associated with therequested application. In an example, the operations include, responsiveto the request, updating code that is stored on the mobile device andthat corresponds to the application logic. In an example, codecorresponding to the application logic is configured to interoperatewith the vehicle head unit responsive to the mobile device receiving auser input, the interoperation according to a result of the execution ofthe instruction by the vehicle head unit.

In an example, a memory device having instructions stored thereon that,in response to execution by a processing device, cause the processingdevice to perform operations is provided. An operation includesreceiving a request for an application of a mobile device to utilize aresource of a vehicle head unit, the request including a first profileof the vehicle head unit and a second profile of the mobile device. Anoperation includes determining whether the requested application isauthorized to utilize the resource of the vehicle head unit based on acurrent status of the vehicle. An operation includes, responsive todetermining that the requested application is authorized to utilize theresource of the vehicle, downloading an instruction to the vehicle headunit, the instruction to be executed by embedded software of the vehiclehead unit so as to enable the requested application to utilize aresource of the vehicle head unit.

In an example, the embedded software comprises a template HMIapplication and a plurality of HMI screens, and the instructiondelineates a specific order to display at least a portion of theplurality of HMI screens for the requested application. In an example,the template HMI application operates without an interpreter component.

In an example, the first profile identifies a first unique identifierthat corresponds to the vehicle head unit and identifies a language orprotocol associated with the embedded software. In an example, thesecond profile identifies a second unique identifier that is differentthan the first unique identifier.

In an example, the instruction comprises a result of a command orcontrol function executed by application logic. In an example, theoperations include, responsive to determining that the requestedapplication is authorized to utilize the resource of the vehicle,updating code that is stored on the mobile device and that correspondsto the application logic. In an example, code corresponding to theapplication logic is configured to interoperate with the vehicle headunit responsive to the mobile device receiving a user input, theinteroperation according to a result of the execution of the instructionby the vehicle head unit.

Referring now to FIG. 16, it illustrates another aspect of the presentdisclosure, namely another system for extending a mobile phone userapplication to utilize an HMI of a vehicle head unit. This simplifieddiagram has three main components, a mobile phone 1640, a motor vehiclehead unit 1620 and a remote server 1670. As indicated in FIG. 16, themobile phone 1640 includes communication capability to conduct packetdata communications 1652, for example, over a mobile network 1654.Various voice and or data services may be used for communications withthe server. The mobile network, in turn, may have a gateway (not shown)to the internet, shown as IP Cloud 1666. The remote server 1670 has acommunications component (not shown) to conduct communications 1668 viathe internet 1666.

Among other things, the arrangement of FIG. 16 enables downloading ofuser applications programs, for example, a user application 1644 showninstalled on the mobile phone 1640, from the server 1670. Other methodsof downloading user application programs were discussed above. It isalso known to acquire a mobile application program from an online “appstore.” In addition, the illustrated system can be used to downloadphone application information (“phone app information”) 1680 located atthe server 1670, to the mobile phone. The phone app information may beprovided on a per user application basis, as further discussed below.The phone app information 1680 may be acquired from, maintained, orupdated from a separate remote server (not shown). In a preferredembodiment, the phone app application information is downloaded to anHAP application program 1642 on the mobile phone.

The motor vehicle head unit 1620 includes an HUP software component 1630which is arranged to conduct communications 1635 with the mobile phone.The head unit proxy 1630 is operatively coupled to the HMI 1622 of thehead unit 1620. For example, the HUP may interact with the HMI viavarious software components and protocols. As discussed above, the HMIof the head unit may include a display screen, which may be a touchscreen, a microphone, speakers and other I/O elements. In thisillustration, the HMI includes one or more generic display screens 1624.We refer here not to the physical display screen, but rather softwareelements that define the appearance and operation of one or more genericscreens. These generic display screens may be used to extend the userinterface of the user application program 1644 executing on the mobilephone 1640 as explained in greater detail below. The head unit and themobile phone may be communicatively coupled by a short range wirelesslink, for example a Bluetooth® link, or other non-contact means such asIR, or by a cable.

Head unit HMI display and associated application logic cannot easily beupdated due to limitations of the head unit platform resources.Consequently, the HMI may not be well adapted to serve as an extendedinterface for newer user application programs that may not have existedat the time that the head unit was manufactured or programmed. In somecases, it may be costly or impractical for the vehicle manufacturer orautomotive OEM to update head unit firmware to accommodate new userapplication programs and their corresponding command and controlfunctionality for the purpose of interacting with the head unit.

Various head unit platforms are known in OEM and aftermarkets. They mayuse various types of embedded processors and operating systems, forexample Windows® Automotive, Android, QNX, etc. The head unit typicallycontains display screens that can be used to display content in apassive manner. That is, the head unit can receive and display content,such as a graphic or picture, or play an audio file, without knowing orunderstanding that content or the meaning of the data that it displays.In addition, typically, the head unit is not capable of managing thestate or use case relative to the state of the application residing onthe phone with which it may be interacting. Thus, the head unit may belikened to a terminal, lacking user application specific business logic.

Typically, a head unit includes input UI elements. Turning to FIG. 21,it shows a simplified example of a head unit 2102 that may be found in amotor vehicle. The head unit in this illustration shows a physicaldisplay screen 2104, which may be a touch screen, and it also includesone or more mechanical buttons or switches 2110, 2112 that may belocated in the bezel or frame surrounding the display screen. Buttons2110 and 2112 illustrate actual physical hardware switches that may bepressed by user's fingers as an input device. The display screen may beused to display data, messages, images, or other content received by thehead unit from the user application as discussed herein. The content mayinclude audio or video data for presentation through the head unit.

Many head units implement generic display templates or layouts. Forexample, a simple template may be provided to display a video and itstitle. Such a template would populate only two regions of a displayscreen, for example, placing the video in a region 2134, and the titleor related information in a text display region or window 2140 below thevideo. Another template may provide for six input buttons. In the caseof mechanical buttons, for example 2110 and 2112, they may be built intothe bezel with three on each side. Text or images may be output to theHMI so as to display a corresponding image, badge or other identifieradjacent to each of the mechanical buttons. These identifiers may bedisplayed, for illustration, in the six regions marked 2120 in thedrawing, corresponding to the six mechanical buttons represented asheptagons. In this way, the function or meaning of the hard button canbe varied by displaying a different identifier adjacent to the hardbutton. In the case that display screen 2104 is touch sensitive (a“touch screen”), the same regions 2120, duly identified, may be used asinput buttons themselves. A generic display template for use with atouch screen may be configured to provide for any predetermined size andarrangement of detectable touch regions. In one example, the HMI wouldthen simply output a message or event that indicates which region waspressed. It need not understand its import.

In general, the head unit 2102 can be used for input to a userapplication program that is executing in a nearby mobile phone, byutilizing the system of FIG. 16. Further, the head unit may have otherinput services or hardware, not shown, such as a microphone to receiveaudible commands. In addition, the head unit may have access to one ormore vehicle networks, for example a CAN network, to acquire informationfrom the vehicle which can also serve as an input to a user application.For example, the vehicle state, such as speed, may be passed on to theHAP for consideration in connection with enforcing safety policies.

In order for a generic HMI of a head unit, and more specifically genericscreen displays, to be used to extend the user interface of anapplication program, information that is specific to the userapplication program must be employed, in order to appropriatelytranslate and map communications between the user application 1644 andthe HMI 1622. That type of information, identified as 1680 in FIG. 16,may be maintained on the remote server 1670 and downloaded upon request.Once that information has been downloaded and stored in the mobilephone, in a manner assessable to the HAP application, it can providethis functionality. More specifically, in preferred embodiments, thedownloaded phone app information 1680 can be used by HAP to managecommand and control flow and state for each use case relative to thesubject application installed on the mobile phone, and the display orother output of data via the head unit. The HAP can output content in aformat appropriate to various generic screen display templates, ortemplate layouts, so that the head unit can display that informationwithout knowledge or logic that is specific to the user application suchas use cases, status and state. Rather, in one preferred embodiment,user application status and state are maintained by the HAP on themobile phone.

FIG. 17 is a functional block diagram illustrating an example ofsoftware components that may be contained in an HAP application, such asthat indicated at 1642 in FIG. 16. In FIG. 17, the HAP 1700 in oneembodiment comprises an API 1702 coupled to an HAP message handlingcomponent 1704. The following components may be implemented usingJavaScript or any suitable scripting language. We will refer toJavaScript by way of illustration. The message handling component mayinclude a JavaScript Interpreter 1706. The JavaScript Interpreter iscommunicatively coupled to individual JavaScript components for one ormore user application programs, shown as “nomadic application_(n)” forexample, component 1710, for applications 1-n. A separate JavaScriptcomponent preferably is provided for each application program ofinterest. Three such JavaScripts are shown in the drawing forillustration although this number is not critical.

Each JavaScript in turn contains or is coupled to access a correspondingtemplate message translator 1712. This will be used for translatingmessages communicated between the mobile phone and the head unit asfurther explained below. The JavaScript components for a given userapplication may be downloaded upon request, as noted earlier, from thephone app information store 1680 on the server 1670. A request to theserver may include an identifier of the user's application program. In apreferred embodiment of this aspect of the invention, the request forphone app information need not identify the head unit or HMIspecifically. It may identify a generic type of head unit or display, ornot identify the head unit at all.

The HAP application 1700 further may include a protocol stack 1720 forcommunications with the head unit. Alternatively, or in addition, theHAP 1700 may include a simpler message framing protocol component 1722,for communication with head units that cannot support a more elaborateprotocols such as HTTP/TCP/IP/SLIP. A protocol discriminator component1730 serves to determine what protocols are applicable and directcommunication accordingly. Finally, the protocol discriminator iscoupled to a suitable communication component 1740.

Each individual JavaScript, for example 1720, implements userapplication logic and message format comprehension that would otherwisebe contained in the associated head unit HMI application unit if it weredesigned for interaction with the corresponding user app. In this case,however, the HMI is not so configured, so it is treated as a genericHMI. A standard “template screen” on the head unit cannot make decisionsor persist applications state. It can only be used to displaycategorized content, for example, lists, basic messages, results and“now playing” screens. For example, referring to FIG. 21, a display area2134 might be used to display selected content as noted. A templatemessage translator may be used to translate the nomadic applicationspecified request and response messages to the format required to thetemplate-based head unit HMI screens. Further, the JavaScript 1710 maycontain button mapping information along with visual buttonidentification data which can be sent to the screen to visually identifythe corresponding button(s), as noted above with reference to FIG. 21,based on the individual phone application represented by the associatedJavaScript.

Referring now to FIG. 18, this shows a simplified diagram illustratingan example of data flow between a user application program and a vehiclehead unit HMI utilizing the integrated HAP application. A userapplication (“nomadic application_(n)”) 1800 interacts with an HAP API1802 arranged to communicated messages to a corresponding JavaScriptprogram 1810 also installed on the mobile phone. The JavaScript 1810includes appropriate user app HMI logic and state management code 1812.Messages 1814 from the user app are formatted as they would be in normaloperation of the user app 1800.

The JavaScript 1810 for user app 1800 further includes a templatemessage translator (“TMT”) component 1820. In operation, the TMTreceives a message from the logic 1812, and translates it into atemplate formatted message, i.e. one compatible with the head unit. Thetemplate formatted message 1824 is then communicated to the head unit1830. Conversely, in the other direction, a template formatted message1834 may be communicated from the head unit to the JavaScript 1810,where it is received by the TMT 1820, and translated to a form useful tothe application logic and state management 1812. The logic may thendetermine to send a message 1840 (user app formatted) to the application1800 via the HAP API. Each request message received from the head unitwill result in one or more transactions between the JavaScript code andthe user application before a result is returned to the head unit.

FIG. 19 comprises a messaging or signaling diagram showing one exampleof interactions among software components in the case of a synchronousmessage, meaning one initiated by the HMI of the head unit. To begin, anevent 1902 is received from a head unit HMI. As a simple example, it maybe a button press, corresponding to PLAY, where a music player app isexecuting on the mobile phone. The event is communicated via the HUP asillustrated in FIG. 16. A JavaScript interrupter 1910 is incorporatedinto the HAP, as shown, including a JavaScript Manager 1912, AbstractJavaScript component 1920, Application JavaScript 1930, and a statusmanager component 1932. The Application JavaScript is specific to theuser application shown as “nomadic application” 1940 which includes anapplication proxy interface 1942. A JavaScript Interrupter of this typeis commonly available in mobile phone SDK's.

The Abstract JavaScript translates the message for the ApplicationJavaScript, and the Application JavaScript 1930 executes its applicationbusiness logic on the HMI event. If a call to the user app isappropriate, a message or call is sent (1950) to the HAP messagehandler. The HAP message handler, in turn, sends the message to the userapp (“invokeApplicationCallback”) 1952. The app sends a response to themessage handler (“aqSendMsg”) 1954. The message handler may translatethe message, and in turn Abstract JavaScript may exercise translatemessage logic to send an appropriate message to the ApplicationJavaScript. The Application JavaScript executes its business logic,stores or updates status and contents 1932, and translates the responseinto a template format to send to the HMI, see 1960.

FIG. 20 comprises a messaging or signaling diagram showing one exampleof interactions among software components in the case of an asynchronousmessage, meaning one initiated by the user application executing on themobile phone. To begin, the app sends a message which is received by theHAP, see 2010. The HAP message handler 2012 sends the message toApplication JavaScript, which will call its logic, store or fetch statusand contents, and if necessary, generate an HMI update message 2030.

In an example, a system is provided. The system includes a vehicle headunit, the head unit implementing at least one type of genericapplication display screen; a server computer, the server computerarranged for communications over a mobile network to a mobile phone;wherein the server computer is further arranged to deliver phoneapplication information associated with a specific user applicationprogram executable on a mobile phone, and the server delivers the phoneapplication information to the mobile phone via the mobile network; andwherein the phone application information enables extending a userinterface of the specific user application program to utilize thegeneric application display screen of the vehicle head unit.

In an example, the system includes an HAP software applicationexecutable in a mobile phone; and an HUP software application executableon the head unit; wherein the HAP and the HUP are arranged tocommunicate messages or events between them, and to utilize aspects ofthe phone application information to enable the specific userapplication program on the mobile phone to interact with the genericapplication display screen of the vehicle head unit. In an example, thehead unit does not install or execute HMI display application logicspecifically developed to interact with the specific user applicationprogram on the mobile phone. In an example, the HAP is arranged to sendone or more of content, text and images to the an HUP for rendering onthe generic application display screen in accordance with apredetermined template layout of the generic application display screen.In an example, the HAP software application and the HUP softwareapplication are each implemented in a scripting language. In an example,the phone application information includes data for implementing asafety policy in connection with execution of the specific userapplication program. In an example, the HAP includes a message handlingcomponent, and at least one protocol stack coupled to the messagehandling component, for communications with the head unit; the messagehandling component includes at least one scripting language componentassociated with a specific user application program; and the scriptinglanguage component includes a corresponding template message translatorcomponent, the message translator component configured for translatingrequest and response messages generated by the corresponding userapplication program into a format compatible with a template-basedgeneric application display screen(s) of a vehicle head unit. In anexample, the scripting language component includes corresponding userapplication logic to obviate specific user application logic in the headunit. In an example, the scripting language component maintainsapplication state for the corresponding user application logic toobviate maintaining state in the head unit.

In an example, a computer-implemented method for use in a mobile phoneis performed. The computer-implemented method includes identifying auser application program installed on a mobile phone; requestinginformation specific to the identified user application from a remoteserver; receiving phone application information downloaded from a remoteserver responsive to the information request, wherein the phoneapplication information enables extending a user interface of theidentified user application program to utilize a generic applicationdisplay screen of a vehicle head unit.

In an example, the computer-implemented method includes installing anHAP software application on the mobile phone; and installing an HUPsoftware application executable on a vehicle head unit; wherein the HAPand the HUP are arranged to communicate messages or events between them,and to utilize aspects of the phone application information to enablethe identified user application program on the mobile phone to interactwith the generic application display screen of the vehicle head unit.

In an example, the computer-implemented method includes, in the HAPsoftware application, translating request and response messagesgenerated by the corresponding user application program into a formatcompatible with a template-based generic application display screen(s)of a vehicle head unit.

In an example, the computer-implemented method includes, in the HAPsoftware application, translating messages or events received from thevehicle head unit into a format compatible with the corresponding userapplication program.

In an example, the computer-implemented method includes, in the HAPsoftware application, translating a request message generated by thecorresponding user application program into a format compatible with atemplate-based generic application display screen(s) of a vehicle headunit so as to render one or more of content, text and images on ageneric application display screen of the vehicle head unit.

In an example, the computer-implemented method includes receiving amessage from the head unit; interacting with the user applicationprogram responsive to the received message; and returning a resultprovided by the user application program to the head unit. In anexample, the computer-implemented method includes translating the resultinto a format compatible with the template-based generic applicationdisplay screen(s) of the vehicle head unit. In an example, thecomputer-implemented method includes translating the button press eventmessage from the head unit based on a current user application programstate and based on a button identifier previously sent to the head unitfor display.

In an example, a method for extending a user interface of a smart phoneuser application to an HMI of a vehicle head unit is provided. Themethod includes installing a user application program in a smart phone;communicatively coupling the smart phone to a head unit of a vehicle;and executing an HAP software component in the smart phone; wherein theHAP includes an API for interfacing to the user application, and aninterface for communicating with a vehicle head unit; receiving in theHAP a button press notification from the head unit-HMI; in the HAP,mapping the button press notification to a UI control specific to theexecuting user application; and in the HAP, communicating the UI controlto the executing user application.

In an example, the mapping is based on a visual button identifierpreviously sent from the HAP to the head unit for display to visuallyidentify a selected button on a generic touch screen display of avehicle head unit.

In an example, the method includes maintaining user application programstatus in the HAP so as to obviate maintaining user application programstatus in the head unit.

Efficient Headunit Communication Integration

HTTP is often the communication approach chosen by designers of invehicle automotive IVI where there is a need for communication betweenthe IVI and applications running on the user's cell phone, and forcommunication between applications running on the IVI and content andconfiguration servers running on the internet or other IP based networkconnection.

In the case where the IVI application needs to communicate with abackend system on the internet or other IP based network connectionusing HTTP, and the IVI is relying on the user cell phone with internetconnection as the communication path for this communication, the user'scell phone includes application that receives HTTP request from the IVIand then on behalf of the IVI application creates an HTTP request to aspecific endpoint over the mobile IP of the cellular network to marshalthe IVI request intent to that end point on the internet.

On this same IP connection the cellphone application will also receivethe response from the endpoint on the internet. Once the response isreceived then the cell phone application will need to send the responseback to the IVI application as if it were the response for the originalpending IVI application request. This approach is needed in order toavoid the added cost imposed by the cellular carrier when using the cellphone as a simple network access device to the internet (PPP->IP->TCP tocellular network).

When a cellphone application acts as an intermediate proxy for HTTPrequests between an IVI application and a backend service, it introducesthe risk of interception or tampering with communication. In such aconfiguration, an IVI application cannot make use of standard transportlevel security mechanisms to ensure its communication with a backendservice is secure since the cellphone application is acting as a“man-in-the-middle”. If security assurances commensurate with transportlevel security are required, custom security must instead be implementedon top of HTTP. This custom security adds to the development cost of thesystem, introduces the likelihood of incompatibility with existingbackend services, and widens the security attack surface of the overallsystem.

When a cellphone application acts as an intermediate proxy for HTTPrequests between the IVI application and the backend, by definition itconstrains the application level protocol that can be used. In such aconfiguration, the IVI is prevented from making use of non-HTTPprotocols. Instead, existing applications must be redesigned to supporttunneling of their requests through HTTP. Tunneling of requests throughHTTP adds to the complexity and cost of the system, and introduces thelikelihood of incompatibility of the system with existing backendservices.

To address the multitude of problems with an HTTP-only proxy solution,an alternate or complementary solution(s) makes use of a TCP or UDPproxy embedded in the cellphone application.

FIG. 22 illustrates a system for efficient headunit communicationintegration.

The system 2200 includes a head unit 2201 and a mobile device 2203. Thehead unit 2201 may include a processing device 2202 configured to coupleto mobile device 2203 and transmit to the mobile device 2203 a requestto utilize a resource of the mobile device. The mobile device 2203 mayinclude a processing device 2204 configured to determine whether toauthorize the request. The processing device 2204 may be configured toutilize a proxy of the mobile device to establish a connection with adestination in response to determining to authorize the request.

FIG. 23 is a simplified communication diagram illustrating a smartphoneapplication enabling data exchange between an IVI and a backend (remoteserver) utilizing SOCKS (SOCKet Secure) Proxy protocol.

In one embodiment, a standard SOCKS (SOCKet Secure) proxy is includedwithin the cellphone application. The SOCKS proxy acts as anintermediary between the IVI environment and the greater IP networkbackend. By proxying data at the TCP or UDP layer, the IVI and backendcan make use of a greater range of network services than is availablewith an HTTP proxy alone.

In an example, head unit 2301 may initiate SOCKS negotiation with mobiledevice 2303 in order to provide a request to utilize a resource of themobile device 2303, e.g. transmit SOCKS request message 2310. Mobiledevice 2303 may be configured to, in response to receiving the request,determine 2313 whether to authorize the request. In an example, therequest may indicate a destination (i.e. server 2305) for the head unit2301 to communicate with using a resource of the mobile device 2303,e.g. a long range transceiver of the mobile device 2303. Mobile device2303 may be configured to determine whether to authorize the requestbased on an identifier associated with the indicated destination. In anexample, mobile device 2303 may be configured to determine whether theidentifier is included in a locally or remotely stored white list, e.g.may be configured to compare the identifier to the white list.

The destination based authorization may be one portion of a policyenforcement scheme. For example, mobile device 2303 may be configured tocheck a subscription/account state associated with the request. Themobile device 2303 may be configured to determine that the request isauthorized if the destination is included in the whitelist and thesubscription/account state corresponds to a predefined state, e.g. anactive state.

The mobile device 2303 may be configured to, in response to determiningto authorize the request, transmit a communication 2316 to establish aconnection with the indicated destination. In an example, the mobiledevice 2303 may be configured to open a socket to the indicateddestination in order to establish a TCP or UDP connection.

The mobile device 2303 may be configured to transmit a SOCKS completionmessage 2319 corresponding to the SOCKS request message 2310. The headunit 2301 may communicate (2322) with the server 2305 via the long rangetransmitter and over the connection 2316.

FIG. 24 is a simplified communication diagram illustrating a smartphoneapplication providing transparent proxy server functionality to enabledata exchange between an IVI and a backend (remote server).

In another example, the head unit 2401 uses a TCP or UDP socket withoutSOCKS negotiation and the mobile device 2403 takes care of transparentlyproxying the TCP or UDP socket to a destination endpoint on the IVI'sbehalf. The head unit 2401 may be configured to transmit a communication2410 to provide a request to utilize a resource of the mobile device2303. For example, the head unit 2401 may be configured to open a socketto a well known port.

The mobile device 2403 may be configured to determine 2413 whether toauthorize the request. In an example, mobile device 2403 may beconfigured to identify the port on which the request is received at themobile device. The mobile device 2403 may be configured to determinewhether a local or remote mapping includes an entry corresponding to theidentified port. The mobile device 2403 may be configured to notauthorize the request in response to determining that the mapping doesnot include the entry. The mobile device 2403 may be configured todiscover a destination in response to determining that the mappingincludes the entry. In an example, the mapping of well known port(s) todestinations is provided by the server 2405.

Similar to the previous example, the destination based authorization maybe one portion of a policy enforcement scheme. For example, mobiledevice 2403 may be configured to check a subscription/account stateassociated with the request. The mobile device 2403 may be configured todetermine that the request is authorized if the mapping includes theentry corresponding to the identified port and the subscription/accountstate corresponds to a predefined state, e.g. an active state.

The mobile device 2403 may be configured to, in response to discoveringthe destination, transmit a communication 2416 to establish a connectionwith the indicated destination. In an example, the mobile device 2403may be configured to open a socket to the discovered destination inorder to establish a TCP or UDP connection.

The mobile device 2303 may be configured to transmit an acknowledgement2419 corresponding to the communication 2410. The head unit 2401 maycommunicate (2422) with the server 2405 via the long range transmitterand over the connection 2416.

In each of the examples described with respect to FIGS. 23 and 24, theIVI application and backend can communicate with added flexibility sincethe application protocol is no longer limited to HTTP, although HTTP isnot precluded. Further, the IVI application and backend can usetransport level security including, but not limited to, Secure SocketLayer (SSL) or Transport Layer Security (TLS) to provide strong securityassurances for communication. In addition, the lack of an intermediateHTTP proxy allows for greater efficiencies when streaming requestsbetween the IVI application and the backend service since theintermediate proxy does not need to parse requests and responses beforeproxying them.

FIG. 25 is a simplified communication diagram illustrating a smartphoneapplication enabling data exchange between an IVI and a backend (remoteserver) utilizing SOCKS Proxy protocol chaining.

In an example, a proxy, e.g. a SOCKS proxy, is included within the HUPand HAP. This is referred to as proxy chaining. The proxy chain acts asan intermediary between the IVI environment and the greater IP networkbackend. By proxying data at the TCP or UDP layer, the IVI and thebackend can make use of a greater range of network services than isavailable with an HTTP proxy alone.

In an example, head unit 2501 may include an IVI application 2502 with aSOCKS proxy client and a SOCKS proxy server 2504. Head unit 2501 mayinitiate SOCKS negotiation with mobile device 2503 in order to provide arequest to utilize a resource of the mobile device 2503, e.g. transmitSOCKS proxy chaining communication 2310 for a SOCKS request messageoriginating from the IVI application 2502.

Head unit 2501 may be configured to perform an initial portion of anauthorization check prior to the transmission of proxy chainingcommunication 2510. For example, head unit 2501 may be configured tocheck subscription/account state, and in an example cause the proxychaining communication 2510 to be transmitted in response to determiningthat the that the subscription/account state corresponds to a predefinedsubscription/account state, e.g. an active subscription/account state.If the subscription/account state does not correspond to the predefinedsubscription/account state, e.g. corresponds to an inactivesubscription/account state, the proxy chaining communication 2510 is nottransmitted.

Mobile device 2503 may be configured to, in response to receiving therequest of the SOCKS proxy chaining communication 2510, determine 2513whether to authorize the request. In an example, the determination bythe mobile device 2503 is a subsequent portion of the authorizationscheme. In an example, the subsequent portion may be based on adestination associated with the request. For example, the request mayindicate a destination (i.e. server 2505) for the head unit 2501 tocommunicate with using a resource of the mobile device 2503, e.g. a longrange transceiver of the mobile device 2503. Mobile device 2503 may beconfigured to determine whether to authorize the request based on anidentifier associated with the indicated destination. In an example,mobile device 2503 may be configured to determine whether the identifieris included in a locally or remotely stored white list, e.g. may beconfigured to compare the identifier to the white list.

In the above example, the enforcement of an authorization scheme isdistributed between the head unit 2501 and the mobile device 2503. Inanother SOCKS Proxy protocol chaining example, the enforcement of anauthorization scheme may be performed by the head unit 2501 or themobile device 2503.

The mobile device 2503 may be configured to, in response to determiningto authorize the request, transmit a communication 2516 to establish aconnection with the indicated destination. In an example, the mobiledevice 2503 may be configured to open a socket to the indicateddestination in order to establish a TCP or UDP connection.

The mobile device 2503 may be configured to transmit a SOCKS completionmessage 2519 corresponding to the SOCKS request message 2510. The headunit 2501 may communicate (2522) with the server 2505 via the long rangetransmitter and over the connection 2516.

FIG. 26 is a simplified communication diagram illustrating a smartphoneapplication providing transparent proxy server functionality to enabledata exchange between an IVI and a backend (remote server) utilizingtransparent proxy chaining.

In another example, IVI applications do not need to implement the SOCKSclient protocol. Instead, the IVI application uses a TCP or UDP socketwithout SOCKS negotiation and the head unit application takes care oftransparently proxy chaining the TCP or UDP socket to a destinationendpoint on the IVI's behalf.

In an example, head unit 2601 may include an IVI application 2602without a SOCKS proxy client and a transparent proxy server 2604. IVIapplication 2602 may open a socket to a well known port in order toinitiate a request to utilize a resource of a remote device.

Similar to the previous example, head unit 2601 may be configured toperform an initial portion of an authorization check prior to openingthe socket to the well known port. For example, head unit 2601 may beconfigured to check subscription/account state, and in an example causesocket to be opened to the well known port in response to determiningthat the subscription/account state corresponds to a predefinedsubscription/account state, e.g. an active subscription/account state.If the subscription/account state does not correspond to the predefinedsubscription/account state, e.g. corresponds to an inactivesubscription/account state, the socket is not opened.

Mobile device 2603 may be configured to, in response to receiving therequest of the SOCKS request message 2610, determine 2613 whether toauthorize the request. In an example, the determination by the mobiledevice 2603 is a subsequent portion of the authorization scheme. In anexample, the subsequent portion may be based on a destination associatedwith the request. For example, the request may indicate a destination(i.e. server 2605) for the head unit 2601 to communicate with using aresource of the mobile device 2603, e.g. a long range transceiver of themobile device 2603. Mobile device 2603 may be configured to determinewhether to authorize the request based on an identifier associated withthe indicated destination. In an example, mobile device 2603 may beconfigured to determine whether the identifier is included in a locallyor remotely stored white list, e.g. may be configured to compare theidentifier to the white list.

In another proxy chaining example, the enforcement of an authorizationscheme may be performed by the head unit 2601 or the mobile device 2603.As an example of the authorization scheme being performed by the headunit 2601, the head unit 2601 may be configured to determine whether toauthorize the request responsive to the opening of the socket. Forexample, head unit 2601 may be configured to identify the port on whichthe request is received at the transparent proxy server 2604. The headunit 2601 may be configured to determine whether a local or remotemapping includes an entry corresponding to the identified port. The headunit 2601 may be configured to not authorize the request in response todetermining that the mapping does not include the entry. The head unit2601 may be configured to discover a destination in response todetermining that the mapping includes the entry. The head unit 2601 maybe configured to share the discovery of the destination with the mobiledevice 2603.

Regardless of which device(s) perform the authorization, the mobiledevice 2603 may be configured to, after the discovery of thedestination, transmit a communication 2616 to establish a connectionwith the indicated destination. In an example, the mobile device 2603may be configured to open a socket to the discovered destination inorder to establish a TCP or UDP connection.

The mobile device 2603 may be configured to transmit a SOCKS completionmessage 2619 corresponding to the communication 2610. The head unit 2601may communicate (2622) with the server 2605 via the long rangetransmitter and over the connection 2616.

In each of the examples described with respect to FIGS. 25 and 26, theIVI application and backend can communicate with added flexibility sincethe application protocol is no longer limited to HTTP, although HTTP isnot precluded. Further, the IVI application and backend can usetransport level security including, but not limited to, SSL or TLS toprovide strong security assurances for communication. In addition, thelack of an intermediate HTTP proxy allows for greater efficiencies whenstreaming requests between the IVI application and the backend servicesince the intermediate proxy does not need to parse requests andresponses before proxying them.

In an example, a method is provided. The method includes coupling amobile device and a vehicle head unit; receiving, at the mobile device,a request for the vehicle head unit to utilize a resource of the mobiledevice; determining, by the mobile device, whether to authorize therequest; and in response to determining to authorize the request,utilizing a proxy of the mobile device to establish a connection with adestination.

In an example, the determining is based on an identifier associated withthe destination. In an example, the method includes determining whetherthe identifier or the destination is included in a white list.

In an example, the method includes identifying a port on which therequest is received at the mobile device; determining whether a mappingincludes an entry corresponding to the identified port; and in responseto determining that the mapping includes the entry, discovering thedestination.

In an example, the proxy of the mobile device comprises a first proxyserver that is different than a second proxy server that transmitted therequest from the vehicle head unit. In an example, the first proxyserver comprises a first SOCKS proxy server. In an example, thedetermining is based on an identifier associated with the destination.In an example, the method includes determining whether the identifier orthe destination is included in a white list. In an example, the methodincludes identifying a port on which the request is received at themobile device; determining whether a mapping includes an entrycorresponding to the identified port; and in response to determiningthat the mapping includes the entry, discovering the destination. In anexample, determining, by the mobile device, whether to authorize therequest further comprises checking a subscription/account stateassociated with the request; and determining to authorize the request inresponse to determining that the mapping includes the entry and thesubscription/account state corresponds to a predefinedsubscription/account state.

In an example, a specially configured memory device is provided. Thememory device has instructions stored thereon that, in response toexecution by a processing device, cause the processing device to performoperations including coupling a mobile device and a vehicle head unit;receiving, at the mobile device, a request for the vehicle head unit toutilize a resource of the mobile device; determining, by the mobiledevice, whether to authorize the request; and in response to determiningto authorize the request, utilizing a proxy of the mobile device toestablish a connection with a destination.

In an example, the determining is based on an identifier associated withthe destination. In an example, the operations include determiningwhether the identifier or the destination is included in a white list.

In an example, the operations include identifying a port on which therequest is received at the mobile device; determining whether a mappingincludes an entry corresponding to the identified port; and in responseto determining that the mapping includes the entry, discovering thedestination.

In an example, the proxy of the mobile device comprises a first proxyserver that is different than a second proxy server that transmitted therequest from the vehicle head unit. In an example, the first proxyserver comprises a first SOCKS proxy server. In an example, thedetermining is based on an identifier associated with the destination.In an example, the operations include determining whether the identifieror the destination is included in a white list. In an example, theoperations include identifying a port on which the request is receivedat the mobile device; determining whether a mapping includes an entrycorresponding to the identified port; and in response to determiningthat the mapping includes the entry, discovering the destination. In anexample, determining, by the mobile device, whether to authorize therequest further comprises checking a subscription/account stateassociated with the request; and determining to authorize the request inresponse to determining that the mapping includes the entry and thesubscription/account state corresponds to a predefinedsubscription/account state.

It will be obvious to those having skill in the art that many changesmay be made to the details of the above-described embodiments withoutdeparting from the underlying principles of the invention. The scope ofthe present invention should, therefore, be determined only by thefollowing claims.

Most of the equipment discussed above comprises hardware and associatedsoftware. For example, the typical navigation device is likely toinclude one or more processors and software executable on thoseprocessors to carry out the operations described. We use the termsoftware herein in its commonly understood sense to refer to programs orroutines (subroutines, objects, plug-ins, etc.), as well as data, usableby a machine or processor. As is well known, computer programs generallycomprise instructions that are stored in machine-readable orcomputer-readable storage media. Some embodiments of the presentinvention may include executable programs or instructions that arestored in machine-readable or computer-readable storage media, such as adigital memory. We do not imply that a “computer” in the conventionalsense is required in any particular embodiment. For example, variousprocessors, embedded or otherwise, may be used in equipment such as thecomponents described herein.

Memory for storing software again is well known. In some embodiments,memory associated with a given processor may be stored in the samephysical device as the processor (“on-board” memory); for example, RAMor FLASH memory disposed within an integrated circuit microprocessor orthe like. In other examples, the memory comprises an independent device,such as an external disk drive, storage array, or portable FLASH keyfob. In such cases, the memory becomes “associated” with the digitalprocessor when the two are operatively coupled together, or incommunication with each other, for example by an I/O port, networkconnection, etc. such that the processor can read a file stored on thememory. Associated memory may be “read only” by design (ROM) or byvirtue of permission settings, or not. Other examples include but arenot limited to WORM, EPROM, EEPROM, FLASH, etc. Those technologies oftenare implemented in solid state semiconductor devices. Other memories maycomprise moving parts, such as a conventional rotating disk drive. Allsuch memories are “machine readable” or “computer-readable” and may beused to store executable instructions for implementing the functionsdescribed herein.

A “software product” refers to a memory device in which a series ofexecutable instructions are stored in a machine-readable form so that asuitable machine or processor, with appropriate access to the softwareproduct, can execute the instructions to carry out a process implementedby the instructions. Software products are sometimes used to distributesoftware. Any type of machine-readable memory, including withoutlimitation those summarized above, may be used to make a softwareproduct. That said, it is also known that software can be distributedvia electronic transmission (“download”), in which case there typicallywill be a corresponding software product at the transmitting end of thetransmission, or the receiving end, or both.

Having described and illustrated the principles of the invention in apreferred embodiment thereof, it should be apparent that the inventionmay be modified in arrangement and detail without departing from suchprinciples. We claim all modifications and variations coming within thespirit and scope of the following claims.

1. A method, comprising: coupling a mobile device and a vehicle headunit; receiving, at the mobile device, a request for the vehicle headunit to utilize a resource of the mobile device; determining, by themobile device, whether to authorize the request; and in response todetermining to authorize the request, utilizing a proxy of the mobiledevice to establish a connection with a destination.